If you're using Mac QB to run more than one pool and are using the same team names and the same schedule for both pools, you can transport the schedule, scores, and/or spreads, for a range of weeks you choose, from one file to the other. You can Import data from an external file to the current file or Export data to the external file from the current file.
The critical factor in importing or exporting from one file to another is that the team names must be the same and in the same order. If they're not, Mac QB may refuse to transport data. Therefore, you should enter the team names in Pool #1 and then create Pool #2 from Pool #1, transferring the teams to the new file. In that way, the two files will always be compatible.
1. From the File Menu, choose "Import from窶ｦ" and select the other file. Mac QB will tell you if the two files are compatible and can exchange data.
2. If the two files are compatible, the Transport Data window will appear. (You do not need to transport data at this time. After you have studied the Transport Data window, click Cancel.) The file name under the Transport Data heading is always the external file. If you are importing data to the current file, it will be preceded by "From" and if you're exporting data from the current file, it will be preceded by "To." The data status listing will also indicate which way the data is to move.
The data status show how many weeks of data for the schedule, spreads, and scores have been entered in the current file, as well as the external file. Use this to decide which weeks' data to move.
There are a few rules that Mac QB follows in moving data, regardless of the beginning and ending week you enter.
A. It will not allow you to skip a week's data for the schedule, scores, or spreads which would leaving that week empty. For example, if you are importing the schedule and have the schedule entered in the current file through week 7 and in the external file through week 11, and you set the beginning week at 9, it will automatically reset it to 8, since starting at 9 would leave the current file with a blank schedule for week 8. The same applies to the spreads and scores.
B. It will not move data for a field beyond the last week for which there is data entered in that field. For example, if you have the schedule entered through week 12, the spread through week 9 and the scores through week 8 and set the beginning week to 8 and the ending week to 12, it will move the schedule for weeks 8-12, the spreads for weeks 8-9 and the scores for week 8. (That's assuming, of course, that you've selected all three fields.)
窶｢ If the two pools do not have the same in common teams with the same names and in the same order, Mac QB will alert you. If you have not entered any player picks, it will ask if you wish to transfer the team names as well.
If you have entered players picks and the team names are not the same for the two files, Mac QB will refuse to transport data. If only two or three teams are different, it will list them as they appear in the external file. It may be that the names are slightly different. In that case, you can select Enter or Change Teams Names from the Pool Menu and remove the differences so the files become compatible.
If Pool A has 30 teams and Pool B has 45 teams, the in common teams are the first 30 teams. The assumption is that the common schedule you'll be using will involve the in common teams only. However, you will be given the option of adding the extra teams to the other file, in case you want to use those in later schedules for both pools.
If you have used some of the extra 15 teams in earlier weeks schedules for Pool B but have decided now to use the same schedule for both pools, you can do so without any ill effects, if you NEVER move data from those earlier weeks. The temptation was to have Mac QB refuse to move data between files of differing numbers of teams, but I decided to leave the safeguards in your hands. Just make sure that you always enter the current week as the beginning week.
If the above scenario applies to your pools, I suggest that you always import data and avoid exporting, as a further safeguard. If you accidentally enter week 1 as the beginning week, you can undo the error if you have imported data to the current file by selecting Revert to Last Saved in the File Menu. However, if you've exported to an external file, then the data has overwritten the file on the disk and can't be changed. Then, you'll have to go to a back-up copy.
窶｢ Records are kept by number, not names. Therefore, the in common teams must have the same names and they must have been entered in the same order. If you entered Notre Dame, Dallas, Denver in that order, all records pertaining to Notre Dame are actually to team #1, for Dallas they are to team #2, for for Denver team #3. In the other pool, if you entered them as Denver, Notre Dame, Dallas, records there for team #1 would be referring to Denver, not Notre Dame. If Mac QB allowed you transport files between the two, not only would the schedule and scores be fouled up (you could have Notre Dame playing Dallas and winning 38-10), but also the players' picks.
NOTE: If you wish to see the order the teams were entered rather than the alphabetical listing, hold down the option key, pull down the Pool Menu and select Enter or Change Team Names. If you click on the Pool Menu before pressing down on the option key, the Mac Event Manager will not report the option key event to Mac QB until after you have closed the team names editing window.
If you created a pool and entered the teams and then created a new file and had it carry over the team names from the first file, then the two will have the same in common teams and in the same order.
窶｢ If your two files are incompatible, and it's not simply a variation in spelling for a team name, then you'll have to accept the fact and wait until next season. DO NOT TRY TO CORRECT THE IMCOMPATIBILITIES BY MOVING TEAM NAMES. Even if you adjust the schedule, scores, spreads and player's picks, there are too many other factors involved. And in spite of your efforts, you'll jumble the file and make it worthless.
